Skip to content

Conversation

@descope
Copy link
Contributor

@descope descope bot commented May 20, 2025

This PR contains the following updates:

Package Type Update Change OpenSSF
pep8-naming (changelog) dev minor 0.14.1 -> 0.15.1 OpenSSF Scorecard

Release Notes

PyCQA/pep8-naming (pep8-naming)

v0.15.1

Compare Source

  • N808 now allows type variable names to start with an underscore.

v0.15.0

Compare Source

  • Add support for Python 3.13.
  • Drop support for Python 3.8.
  • N808 checks type variable names use the CapWords convention and have an appropriate suffix.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@descope descope bot added the renovate label May 20, 2025
@descope descope bot enabled auto-merge (squash) May 20, 2025 14:42
@descope
Copy link
Contributor Author

descope bot commented May 20, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...


The current project's supported Python range (>=3.8.1,<4.0) is not compatible with some of the required packages Python requirement:
  - pep8-naming requires Python >=3.9, so it will not be satisfied for Python >=3.8.1,<3.9

Because descope depends on pep8-naming (0.15.1) which requires Python >=3.9, version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pep8-naming, a possible solution would be to set the `python` property to ">=3.9,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 6f99e4e to 516a1d6 Compare May 20, 2025 17:11
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 516a1d6 to 2056e7c Compare May 21, 2025 14:42
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 2056e7c to 9c234f7 Compare May 23, 2025 10:38
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 9c234f7 to 083162f Compare May 23, 2025 19:41
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 083162f to 0b5fa75 Compare May 25, 2025 15:50
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 0b5fa75 to 52e8d01 Compare May 25, 2025 21:22
descope-approve[bot]
descope-approve bot previously approved these changes May 25, 2025
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 52e8d01 to 5f44baa Compare May 26, 2025 21:21
@descope descope bot changed the title chore(deps): update dependency pep8-naming to v0.15.0 chore(deps): update dependency pep8-naming to v0.15.1 May 26, 2025
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 5f44baa to 1512808 Compare May 28, 2025 07:22
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 1512808 to a0af9be Compare June 1, 2025 01:03
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from a0af9be to 3c5b25f Compare June 2, 2025 23:39
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 3c5b25f to a021892 Compare June 3, 2025 20:33
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from a021892 to 86e5dce Compare June 7, 2025 19:34
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 48889b7 to 5c5c755 Compare October 12, 2025 14:57
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 5c5c755 to 8d81b86 Compare October 12, 2025 15:02
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 8d81b86 to 9309fcc Compare October 18, 2025 19:21
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 9309fcc to 9218ae3 Compare October 22, 2025 16:27
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 9218ae3 to c300d55 Compare October 26, 2025 05:53
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from c300d55 to aa9614c Compare October 26, 2025 16:14
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from aa9614c to 2fe8b92 Compare October 26, 2025 23:00
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 2fe8b92 to 57a5ac5 Compare October 30, 2025 19:52
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 57a5ac5 to 909c4b9 Compare October 30, 2025 22:34
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 909c4b9 to fc504bc Compare November 2, 2025 15:31
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from fc504bc to 0398c54 Compare November 2, 2025 23:42
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 0398c54 to 39fa422 Compare November 4, 2025 05:47
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from 39fa422 to bff99cd Compare November 4, 2025 09:57
@descope descope bot force-pushed the renovate/pep8-naming-0.x branch from bff99cd to 0b2be0d Compare November 5, 2025 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant